@lucianonet - this fixes the config save issue. Can you give me some more info about the issue you're seeing with CasC to see if it is related?

EDIT: Re-reading your question from the other commit -- I think that yes, that old PR did break your existing CasC configuration. This version (2.3.1) should have been a breaking version instead of a simple bugfix version.

Here is an example of the CasC config that works with the recently security-fixed version - https://github.com/jenkinsci/keycloak-plugin/blob/master/src/test/resources/org/jenkinsci/plugins/casc.yaml :

jenkins:
  securityRealm:
    keycloak:
      keycloakJson: |-
        {
          "realm": "master",
          "auth-server-url": "https://keycloak.example.com/auth/",
          "ssl-required": "external",
          "resource": "ci-example-com",
          "credentials": {
            "secret": "secret-secret-secret"
          },
          "confidential-port": 0
        }
      keycloakRespectAccessTokenTimeout: true
      keycloakValidate: false

So instead of being unclassified it is now part of the security realm configuration area. I will look to see how I can mark this keycloak update as being breaking.

@lucianonet - this fixes the config save issue. Can you give me some more info about the issue you're seeing with CasC to see if it is related?

EDIT: Re-reading your question from the other commit -- I think that yes, that old PR did break your existing CasC configuration. This version (2.3.1) should have been a breaking version instead of a simple bugfix version.

Here is an example of the CasC config that works with the recently security-fixed version - https://github.com/jenkinsci/keycloak-plugin/blob/master/src/test/resources/org/jenkinsci/plugins/casc.yaml :

jenkins:
  securityRealm:
    keycloak:
      keycloakJson: |-
        {
          "realm": "master",
          "auth-server-url": "https://keycloak.example.com/auth/",
          "ssl-required": "external",
          "resource": "ci-example-com",
          "credentials": {
            "secret": "secret-secret-secret"
          },
          "confidential-port": 0
        }
      keycloakRespectAccessTokenTimeout: true
      keycloakValidate: false

So instead of being unclassified it is now part of the security realm configuration area. I will look to see how I can mark this keycloak update as being breaking.

@mrmateo Thank you. It's working now.